home *** CD-ROM | disk | FTP | other *** search
UUUUSSSSCCCCOOOONNNNFFFFIIIIGGGG((((3333PPPP)))) UUUUSSSSCCCCOOOONNNNFFFFIIIIGGGG((((3333PPPP)))) NNNNAAAAMMMMEEEE _uuuu_ssss_cccc_oooo_nnnn_ffff_iiii_gggg - semaphore and lock arena configuration operations CCCC SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS ####iiiinnnncccclllluuuuddddeeee <<<<uuuulllloooocccckkkkssss....hhhh>>>> _pppp_tttt_rrrr_dddd_iiii_ffff_ffff______tttt _uuuu_ssss_cccc_oooo_nnnn_ffff_iiii_gggg _((((_iiii_nnnn_tttt _c_m_d_,,,, _...._...._...._))))_;;;; DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN _uuuu_ssss_cccc_oooo_nnnn_ffff_iiii_gggg is used to configure the use of semaphores and locks. Some of these options set configurable parameters to be used on the next _uuuu_ssss_iiii_nnnn_iiii_tttt(3P), others give back information about a particular arena. In the discussion below, arguments to _uuuu_ssss_cccc_oooo_nnnn_ffff_iiii_gggg are numbered starting from 1, thus the first argument refers to _c_m_d. Many of the options require an arena pointer which is the value returned by a successful call to _uuuu_ssss_iiii_nnnn_iiii_tttt and is always interpreted as a _uuuu_ssss_pppp_tttt_rrrr______tttt _****. The following _c_m_ds are available: CCCCOOOONNNNFFFF____IIIINNNNIIIITTTTSSSSIIIIZZZZEEEE Sets the shared segment size (in bytes) for semaphores, locks, and the _uuuu_ssss_mmmm_aaaa_llll_llll_oooo_cccc(3P) arena to the value given by the second argument interpreted as an uuuunnnnssssiiiiggggnnnneeeedddd iiiinnnntttt. The initial value is 65536 bytes. This only has effect if called before a _uuuu_ssss_iiii_nnnn_iiii_tttt(3P). It returns the previously set value. CCCCOOOONNNNFFFF____IIIINNNNIIIITTTTUUUUSSSSEEEERRRRSSSS Sets the maximum number of users for a given group of semaphores and locks to the value given by the second argument interpreted as an uuuunnnnssssiiiiggggnnnneeeedddd iiiinnnntttt. The maximum allowable is 10000 users, and the initial value is 8. This only has effect if called before _uuuu_ssss_iiii_nnnn_iiii_tttt(3P). Each process that calls _uuuu_ssss_iiii_nnnn_iiii_tttt(3P) is considered a user, as is each shared address process that uses a spinlock or semaphore without calling _uuuu_ssss_iiii_nnnn_iiii_tttt(3P). It returns the previously set value. CCCCOOOONNNNFFFF____GGGGEEEETTTTSSSSIIIIZZZZEEEE Returns the arena size (in bytes) for the arena specified by the second argument interpreted as an uuuussssppppttttrrrr____tttt ****. (as returned by _u_s_i_n_i_t(3P)). CCCCOOOONNNNFFFF____GGGGEEEETTTTUUUUSSSSEEEERRRRSSSS Returns the maximum number of users for the arena specified by the second argument interpreted as an uuuussssppppttttrrrr____tttt ****. (as returned by _u_s_i_n_i_t(3P)). CCCCOOOONNNNFFFF____LLLLOOOOCCCCKKKKTTTTYYYYPPPPEEEE The second argument interpreted as an uuuunnnnssssiiiiggggnnnneeeedddd iiiinnnntttt. defines which of UUUUSSSS____NNNNOOOODDDDEEEEBBBBUUUUGGGG, UUUUSSSS____DDDDEEEEBBBBUUUUGGGG, or UUUUSSSS____DDDDEEEEBBBBUUUUGGGGPPPPLLLLUUUUSSSS locks are to be used in the arena set up by the next call to _uuuu_ssss_iiii_nnnn_iiii_tttt(3P). The UUUUSSSS____NNNNOOOODDDDEEEEBBBBUUUUGGGG option is the fastest, and no debugging or metering information is available. UUUUSSSS____DDDDEEEEBBBBUUUUGGGG locks provide metering and PPPPaaaaggggeeee 1111 UUUUSSSSCCCCOOOONNNNFFFFIIIIGGGG((((3333PPPP)))) UUUUSSSSCCCCOOOONNNNFFFFIIIIGGGG((((3333PPPP)))) debugging information about each lock transaction. The metering information gathered consists of - the number of times the lock is requested (_l_m__t_r_i_e_s); the number of times the lock is acquired (_l_m__h_i_t_s); and the number of times the lock was found locked (_l_m__s_p_i_n_s). The metering is stored in a _l_o_c_k_m_e_t_e_r__t structure and is retrievable via _uuuu_ssss_cccc_tttt_llll_llll_oooo_cccc_kkkk(3P). The debugging information maintained consists of the process id of the owner of the lock (_l_d__o_w_n_e_r__p_i_d). The pid is set to -1 if no one owns the lock. The debug info is stored in a _l_o_c_k_d_e_b_u_g__t structure and is retrievable via _uuuu_ssss_cccc_tttt_llll_llll_oooo_cccc_kkkk(3P). The UUUUSSSS____DDDDEEEEBBBBUUUUGGGGPPPPLLLLUUUUSSSS option provides the same debugging and metering information and in addition, if either an unset lock is unlocked, a set lock is unlocked by other than the setter, or a lock is locked twice by the same caller, a message is printed to _s_t_d_e_r_r. CCCCOOOONNNNFFFF____AAAARRRREEEENNNNAAAATTTTYYYYPPPPEEEE By default, arenas are configured so that unrelated processes may join the arena by specifying the appropriate file name when calling _uuuu_ssss_iiii_nnnn_iiii_tttt(3P). This means that the file must continue to exist for the duration of the time the arena is in use. If the file is a temporary file, it may be difficult for an application program to guarantee the file gets removed at the appropriate time. If the second argument interpreted as an uuuunnnnssssiiiiggggnnnneeeedddd iiiinnnntttt. is set to UUUUSSSS____SSSSHHHHAAAARRRREEEEDDDDOOOONNNNLLLLYYYY then _uuuu_ssss_iiii_nnnn_iiii_tttt(3P) will unlink the file after it has opened it. This of course means that unrelated processes may NEVER join the arena. This also implies that all users of the arena must be sharing file descriptors, either by using the PPPPRRRR____SSSSFFFFDDDDSSSS option to _ssss_pppp_rrrr_oooo_cccc(2)), or being related via _ffff_oooo_rrrr_kkkk(2). Note however that processes related via _ffff_oooo_rrrr_kkkk share file descriptors only at _ffff_oooo_rrrr_kkkk time, thus the arena must be set up by the parent process before any children are spawned. Note that if a child is spawned before an arena is set up, and the arena type is set to UUUUSSSS____SSSSHHHHAAAARRRREEEEDDDDOOOONNNNLLLLYYYY and both the parent and child call _uuuu_ssss_iiii_nnnn_iiii_tttt on the same filename, they will get separate arenas - probably not the desired result. CCCCOOOONNNNFFFF____CCCCHHHHMMMMOOOODDDD Sets the access permissions on the arena and lock files. When _uuuu_ssss_iiii_nnnn_iiii_tttt(3P) creates an arena, the user and group ids are set to the callers effective user and group id, and the access permissions are set to 0600. This makes the arena available only to processes running with the same effective user id. To allow other user or group ids access to the arena, the mode on the various files and locks may be changed by using the CCCCOOOONNNNFFFF____CCCCHHHHMMMMOOOODDDD option. The second argument, interpreted as an uuuussssppppttttrrrr____tttt ****. specifies which arena, and the third argument, interpreted as an mmmmooooddddeeee____tttt specifies the new mode (see _c_h_m_o_d(2)). Access to pollable semaphores is governed on a per semaphore basis and is set when first opening the semaphore via _uuuu_ssss_oooo_pppp_eeee_nnnn_pppp_oooo_llll_llll_ssss_eeee_mmmm_aaaa(3P). PPPPaaaaggggeeee 2222 UUUUSSSSCCCCOOOONNNNFFFFIIIIGGGG((((3333PPPP)))) UUUUSSSSCCCCOOOONNNNFFFFIIIIGGGG((((3333PPPP)))) CCCCOOOONNNNFFFF____AAAATTTTTTTTAAAACCCCHHHHAAAADDDDDDDDRRRR Sets the virtual address where the arena and locks are attached in the calling process to the value specified by the second argument, taken as a vvvvooooiiiidddd ****. It must be a multiple of the underlying page size (see _gggg_eeee_tttt_pppp_aaaa_gggg_eeee_ssss_iiii_zzzz_eeee(2)). Normally, when _uuuu_ssss_iiii_nnnn_iiii_tttt(3P) is called, the arena and lock area are attached (via _mmmm_mmmm_aaaa_pppp(2)) using the option that lets the system pick an appropriate attach address. This may not be appropriate if the original creator of the arena is a small process (small code space) and a very large code space unrelated process attempts to attach to the arena. This option allows the creator to fix an address that is acceptable to all processes wishing to join the arena. Note that it is important after calling _uuuu_ssss_iiii_nnnn_iiii_tttt(3P) to reset the attach address to the initial value (_((((_vvvv_oooo_iiii_dddd _****_)))) _~~~~_0000) before another _uuuu_ssss_iiii_nnnn_iiii_tttt(3P) is called. Otherwise the second call will fail. When _ssss_pppp_rrrr_oooo_cccc(2) is called, an arena used to protect standard I/O is set up automatically. By specifying a new attach address before first calling _ssss_pppp_rrrr_oooo_cccc(2) the location of the I/O arena may be fixed. This only has effect if called before a _uuuu_ssss_iiii_nnnn_iiii_tttt(3P). It returns the previously set value. CCCCOOOONNNNFFFF____AAAAUUUUTTTTOOOOGGGGRRRROOOOWWWW If the second argument, interpreted as an uuuunnnnssssiiiiggggnnnneeeedddd iiiinnnntttt, is zero then the underlying file of a newly created arena will be grown to its maximum size (as specified by CCCCOOOONNNNFFFF____IIIINNNNIIIITTTTSSSSIIIIZZZZEEEE) before the arena is mapped in. The arena will be mapped without the _MMMM_AAAA_PPPP______AAAA_UUUU_TTTT_OOOO_GGGG_RRRR_OOOO_WWWW option to _mmmm_mmmm_aaaa_pppp(2). If the second argument is non- zero the file will be mapped with the _MMMM_AAAA_PPPP______AAAA_UUUU_TTTT_OOOO_GGGG_RRRR_OOOO_WWWW option. This can cause some unexpected failures if the underlying file system fills up. The default is to map all files with the _MMMM_AAAA_PPPP______AAAA_UUUU_TTTT_OOOO_GGGG_RRRR_OOOO_WWWW option. This only has effect if called before a _uuuu_ssss_iiii_nnnn_iiii_tttt(3P). It returns the previously set value. CCCCOOOONNNNFFFF____AAAAUUUUTTTTOOOORRRREEEESSSSVVVV If the second argument, interpreted as an uuuunnnnssssiiiiggggnnnneeeedddd iiiinnnntttt, is non- zero then the arena file will be mapped in with the _MMMM_AAAA_PPPP______AAAA_UUUU_TTTT_OOOO_RRRR_EEEE_SSSS_RRRR_VVVV option to _mmmm_mmmm_aaaa_pppp(2). This option is only effective when auto- growing the arena (see _CCCC_OOOO_NNNN_FFFF______AAAA_UUUU_TTTT_OOOO_GGGG_RRRR_OOOO_WWWW above) and the arena file is the special device _////_dddd_eeee_vvvv_////_zzzz_eeee_rrrr_oooo. These two options together permit declaring arenas that are very large on systems with limited resources, and only encountering errors if in fact the application actually uses too much memory. This only has effect if called before a _uuuu_ssss_iiii_nnnn_iiii_tttt(3P). It returns the previously set value. CCCCOOOONNNNFFFF____HHHHIIIISSSSTTTTOOOONNNN Enable semaphore history logging for the arena given by the second argument interpreted as an uuuussssppppttttrrrr____tttt ****. The history mechanism may then be enabled for previously allocated semaphores using _uuuu_ssss_cccc_tttt_llll_ssss_eeee_mmmm_aaaa(3P). All subsequent semaphores allocated via _uuuu_ssss_nnnn_eeee_wwww_ssss_eeee_mmmm_aaaa(3P) are set to log their history. This _c_m_d serves as a global flag on the history mechanism in conjunction with PPPPaaaaggggeeee 3333 UUUUSSSSCCCCOOOONNNNFFFFIIIIGGGG((((3333PPPP)))) UUUUSSSSCCCCOOOONNNNFFFFIIIIGGGG((((3333PPPP)))) CCCCOOOONNNNFFFF____HHHHIIIISSSSTTTTOOOOFFFFFFFF to allow for quick enabling and disabling of history. The history mechanism logs the operation, the semaphore for which the operation was done, the pid of the process performing the operation, and the address from which the operation was called. No history is maintained for locks, since the number of transactions on locks is typically large. CCCCOOOONNNNFFFF____HHHHIIIISSSSTTTTSSSSIIIIZZZZEEEE Set the maximum number of history records kept for the arena specified by the second argument interpreted as an uuuussssppppttttrrrr____tttt ****. to the value of the third argument, interpreted as an uuuunnnnssssiiiiggggnnnneeeedddd iiiinnnntttt. If set to 0 (the initial value) then new history records are allocated until there is no more room in the arena. CCCCOOOONNNNFFFF____HHHHIIIISSSSTTTTFFFFEEEETTTTCCCCHHHH Fills in a history structure for the arena specified by the second argument interpreted as an uuuussssppppttttrrrr____tttt ****. The third argument, interpreted as a hhhhiiiissssttttppppttttrrrr____tttt ****, should point to storage where the history data can be copied to. This structure contains - the number of entries in the history list ( _h_p__e_n_t_r_i_e_s); a pointer to the most recent history structure ( _h_p__c_u_r_r_e_n_t); and the number of non-logged entries due to either lack of space or exceeding the maximum number of entries specified by CCCCOOOONNNNFFFF____HHHHIIIISSSSTTTTSSSSIIIIZZZZEEEE( _h_p__e_r_r_o_r_s). The history list is a doubly linked and NNNNUUUULLLLLLLL terminated list so that the user can then traverse the list as they see fit. Traversing the list from _h_p__c_u_r_r_e_n_t through _h__l_a_s_t will access the list from most recent semaphore event to least recent. If no more space is available in the arena, the oldest history event is re-used. The hhhhiiiisssstttt____tttt structure (defined in _<<<<_uuuu_llll_oooo_cccc_kkkk_ssss_...._hhhh_>>>>) is described below. CCCCOOOONNNNFFFF____HHHHIIIISSSSTTTTOOOOFFFFFFFF Disable the history mechanism for all semaphores in the arena specified by the second argument interpreted as an uuuussssppppttttrrrr____tttt ****. Note that this simply turns off a global history flag for the given arena - the individual semaphores' history state is unaffected. CCCCOOOONNNNFFFF____HHHHIIIISSSSTTTTRRRREEEESSSSEEEETTTT Reinitializes the history chain for the arena specified by the second argument interpreted as an uuuussssppppttttrrrr____tttt ****. to contain no entries. This frees all previously allocated history records. CCCCOOOONNNNFFFF____SSSSTTTTHHHHRRRREEEEAAAADDDDIIIIOOOOOOOOFFFFFFFF By default, the _s_t_d_i_o(3) routines available with _l_i_b_c._a are single threaded. Multiple shared address space processes may attempt to execute them simultaneously and the system guarantees that they will work as expected. This requires that the _s_t_d_i_o(3) data structures be locked on each access, thereby adding overhead which may be unnecessary in certain applications. This command turns off any single threading of the following routines: _g_e_t_c, _p_u_t_c, _f_g_e_t_c, _f_p_u_t_c, _u_n_g_e_t_c, _g_e_t_w, _p_u_t_w, _g_e_t_s, _f_g_e_t_s, _p_u_t_s, _f_p_u_t_s, PPPPaaaaggggeeee 4444 UUUUSSSSCCCCOOOONNNNFFFFIIIIGGGG((((3333PPPP)))) UUUUSSSSCCCCOOOONNNNFFFFIIIIGGGG((((3333PPPP)))) _f_o_p_e_n, _f_d_o_p_e_n, _f_r_e_o_p_e_n, _f_t_e_l_l, _r_e_w_i_n_d, _f_e_o_f, _c_l_e_a_r_e_r_r, _f_e_r_r_o_r, _s_e_t_b_u_f, _s_e_t_l_i_n_e_b_u_f, _s_e_t_b_u_f_f_e_r, _s_e_t_v_b_u_f, _f_c_l_o_s_e, _f_f_l_u_s_h, _f_r_e_a_d, _f_w_r_i_t_e, _f_s_e_e_k, _f_g_e_t_p_o_s, _f_s_e_t_p_o_s, _f_l_o_c_k_f_i_l_e, _f_u_n_l_o_c_k_f_i_l_e, _t_e_m_p_n_a_m, _t_m_p_n_a_m, _t_m_p_f_i_l_e, _m_k_t_e_m_p, _m_k_s_t_e_m_p, _p_o_p_e_n, _p_c_l_o_s_e, _a_t_e_x_i_t, _p_r_i_n_t_f, _f_p_r_i_n_t_f, _v_p_r_i_n_t_f, _v_f_p_r_i_n_t_f, _s_c_a_n_f, _f_s_c_a_n_f, The previous state of _s_t_d_i_o(3) single threading is returned. Note: for FORTRAN the default is different, see _CCCC_OOOO_NNNN_FFFF______SSSS_TTTT_HHHH_RRRR_EEEE_AAAA_DDDD_IIII_OOOO_OOOO_NNNN below. CCCCOOOONNNNFFFF____SSSSTTTTHHHHRRRREEEEAAAADDDDIIIIOOOOOOOONNNN This option enables single threading of the _s_t_d_i_o(3) routines. The previous state of _s_t_d_i_o(3) single threading is returned. Note: The FORTRAN I/O library is not safe for multi-processing, even if the _s_t_d_i_o(3) routines are single threaded. For this reason, FORTRAN programs have _CCCC_OOOO_NNNN_FFFF______SSSS_TTTT_HHHH_RRRR_EEEE_AAAA_DDDD_IIII_OOOO_OOOO_FFFF_FFFF configured by default, to avoid the extra overhead. If a FORTRAN program wishes to use the _s_t_d_i_o(3) routines to get parallel I/O, you must set _CCCC_OOOO_NNNN_FFFF______SSSS_TTTT_HHHH_RRRR_EEEE_AAAA_DDDD_IIII_OOOO_OOOO_NNNN to re-enable the single threading. CCCCOOOONNNNFFFF____SSSSTTTTHHHHRRRREEEEAAAADDDDMMMMIIIISSSSCCCCOOOOFFFFFFFF Some routines besides _s_t_d_i_o(3) routines are also single threaded by default. This option disables this for the following routines: _o_p_e_n_d_i_r, _r_e_a_d_d_i_r, _s_c_a_n_d_i_r, _s_e_e_k_d_i_r, _c_l_o_s_e_d_i_r, _t_e_l_l_d_i_r, _d_u_p_2, _s_r_a_n_d, _r_a_n_d, _a_d_d_s_e_v, _a_d_d_s_e_v_e_r_i_t_y, _f_m_t_m_s_g, _s_e_t_c_a_t, _g_e_t_t_x_t, _l_f_m_t, _l_o_c_a_l_e_c_o_n_v, _n_l__l_a_n_g_i_n_f_o, _p_f_m_t, _s_e_t_l_a_b_e_l, _s_e_t_l_o_c_a_l_e, _s_t_r_f_t_i_m_e, _s_t_r_x_f_r_m, _s_t_r_c_o_l_l, _v_l_f_m_t, _v_p_f_m_t The previous state of single threading is returned. CCCCOOOONNNNFFFF____SSSSTTTTHHHHRRRREEEEAAAADDDDMMMMIIIISSSSCCCCOOOONNNN This option enables single threading of the miscellaneous routines mentioned above. This command is the inverse of CCCCOOOONNNNFFFF____SSSSTTTTHHHHRRRREEEEAAAADDDDMMMMIIIISSSSCCCCOOOOFFFFFFFF. The previous state of single threading of the miscellaneous routines is returned. CCCCOOOONNNNFFFF____SSSSTTTTHHHHRRRREEEEAAAADDDDMMMMAAAALLLLLLLLOOOOCCCCOOOOFFFFFFFF The _m_a_l_l_o_c(3) routines are single threaded by default. This option disables single threading for the following routines: _m_a_l_l_o_c, _f_r_e_e, _r_e_a_l_l_o_c, _c_a_l_l_o_c, _m_a_l_l_o_p_t, _m_a_l_l_i_n_f_o. The previous state of their single threading is returned. CCCCOOOONNNNFFFF____SSSSTTTTHHHHRRRREEEEAAAADDDDMMMMAAAALLLLLLLLOOOOCCCCOOOONNNN This option enables single threading of the _m_a_l_l_o_c(3) routines. The previous state of single threading is returned. The CCCCOOOONNNNFFFF____IIIINNNNIIIITTTTSSSSIIIIZZZZEEEE, CCCCOOOONNNNFFFF____AAAARRRREEEENNNNAAAATTTTYYYYPPPPEEEE, CCCCOOOONNNNFFFF____AAAAUUUUTTTTOOOOGGGGRRRROOOOWWWW, CCCCOOOONNNNFFFF____AAAAUUUUTTTTOOOORRRREEEESSSSVVVV, CCCCOOOONNNNFFFF____AAAATTTTTTTTAAAACCCCHHHHAAAADDDDDDDDRRRR, CCCCOOOONNNNFFFF____LLLLOOOOCCCCKKKKTTTTYYYYPPPPEEEE, and CCCCOOOONNNNFFFF____IIIINNNNIIIITTTTUUUUSSSSEEEERRRRSSSS only take effect if the caller is the process that first sets up the arena. If the process is just joining an existing arena, the settings of these parameters is ignored. PPPPaaaaggggeeee 5555 UUUUSSSSCCCCOOOONNNNFFFFIIIIGGGG((((3333PPPP)))) UUUUSSSSCCCCOOOONNNNFFFFIIIIGGGG((((3333PPPP)))) The structure declaration of hhhhiiiisssstttt____tttt is: typedef struct { struct usema_s *h_sem; /* the semaphore */ int h_op; /* the operation */ pid_t h_pid; /* the thread process id */ int h_scnt; /* the value of the semaphore */ pid_t h_wpid; /* the waking process id */ char *h_cpc; /* the calling PC */ struct hist_s *h_next; /* the next hist_t in the chain */ struct hist_s *h_last; /* the previous hist_t in the chain */ } hist_t; _h__s_e_m is the address of the semaphore. _h__n_e_x_t and _h__l_a_s_t are the linkages that chain all the history records together. _h__o_p defines what operation was performed on the semaphore. Valid operation types are defined in <_u_l_o_c_k_s._h>. _h__p_i_d is the process id of the caller making the semaphore call. _h__s_c_n_t is the semaphore count at the end of the operation. For the HHHHOOOOPPPP____PPPPWWWWOOOOKKKKEEEE operation type, the count is the current semaphore count at the time the process ran after being woken. Pollable semaphores will never record a HHHHOOOOPPPP____PPPPWWWWOOOOKKKKEEEE event. _h__w_p_i_d is the process id of the process to next receive the semaphore. It is only valid for the HHHHOOOOPPPP____VVVVWWWWAAAAKKKKEEEE operation. _h__c_p_c is the address in the callers code that the semaphore operation was called from. The structure declaration of hhhhiiiissssttttppppttttrrrr____tttt is: typedef struct histptr_s { hist_t *hp_current; /* pointer to the last hist_t */ int hp_entries; /* count of hist_t structs */ int hp_errors; /* # of errors due to lack of space */ } histptr_t; _uuuu_ssss_cccc_oooo_nnnn_ffff_iiii_gggg will fail if one or more of the following are true: _EEEE_IIII_NNNN_VVVV_AAAA_LLLL _c_m_d is not a valid command. _EEEE_IIII_NNNN_VVVV_AAAA_LLLL _c_m_d is equal to CCCCOOOONNNNFFFF____IIIINNNNIIIITTTTSSSSIIIIZZZZEEEE and the second argument is less than the system-imposed minimum (4096 bytes) or greater than the system-imposed maximum size for a mapped memory segment. _EEEE_IIII_NNNN_VVVV_AAAA_LLLL _c_m_d is equal to CCCCOOOONNNNFFFF____IIIINNNNIIIITTTTUUUUSSSSEEEERRRRSSSS and the second argument is greater than the system-imposed maximum (10000). _EEEE_IIII_NNNN_VVVV_AAAA_LLLL _c_m_d is equal to CCCCOOOONNNNFFFF____AAAARRRREEEENNNNAAAATTTTYYYYPPPPEEEE and the second argument is not equal to either UUUUSSSS____SSSSHHHHAAAARRRREEEEDDDDOOOONNNNLLLLYYYY or UUUUSSSS____GGGGEEEENNNNEEEERRRRAAAALLLL. _EEEE_IIII_NNNN_VVVV_AAAA_LLLL _c_m_d is equal to CCCCOOOONNNNFFFF____HHHHIIIISSSSTTTTFFFFEEEETTTTCCCCHHHH and history is not currently enabled. PPPPaaaaggggeeee 6666 UUUUSSSSCCCCOOOONNNNFFFFIIIIGGGG((((3333PPPP)))) UUUUSSSSCCCCOOOONNNNFFFFIIIIGGGG((((3333PPPP)))) SSSSEEEEEEEE AAAALLLLSSSSOOOO _cccc_hhhh_mmmm_oooo_dddd(2), _uuuu_ssss_cccc_tttt_llll_llll_oooo_cccc_kkkk(3P), _uuuu_ssss_cccc_tttt_llll_ssss_eeee_mmmm_aaaa(3P), _uuuu_ssss_iiii_nnnn_iiii_tttt(3P), _uuuu_ssss_iiii_nnnn_iiii_tttt_llll_oooo_cccc_kkkk(3P), _uuuu_ssss_iiii_nnnn_iiii_tttt_ssss_eeee_mmmm_aaaa(3P), _uuuu_ssss_mmmm_aaaa_llll_llll_oooo_cccc(3P), _uuuu_ssss_nnnn_eeee_wwww_llll_oooo_cccc_kkkk(3P), _uuuu_ssss_nnnn_eeee_wwww_ssss_eeee_mmmm_aaaa(3P), _uuuu_ssss_nnnn_eeee_wwww_pppp_oooo_llll_llll_ssss_eeee_mmmm_aaaa(3P). DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS Upon successful completion, the return value is dependent on the particular command. CCCCOOOONNNNFFFF____AAAAUUUUTTTTOOOORRRREEEESSSSVVVV, CCCCOOOONNNNFFFF____AAAAUUUUTTTTOOOOGGGGRRRROOOOWWWW, CCCCOOOONNNNFFFF____AAAATTTTTTTTAAAACCCCHHHHAAAADDDDDDDDRRRR, CCCCOOOONNNNFFFF____SSSSTTTTHHHHRRRREEEEAAAADDDDMMMMAAAALLLLLLLLOOOOCCCCOOOOFFFFFFFF, CCCCOOOONNNNFFFF____SSSSTTTTHHHHRRRREEEEAAAADDDDMMMMAAAALLLLLLLLOOOOCCCCOOOONNNN, CCCCOOOONNNNFFFF____SSSSTTTTHHHHRRRREEEEAAAADDDDMMMMIIIISSSSCCCCOOOOFFFFFFFF, CCCCOOOONNNNFFFF____SSSSTTTTHHHHRRRREEEEAAAADDDDMMMMIIIISSSSCCCCOOOONNNN, CCCCOOOONNNNFFFF____SSSSTTTTHHHHRRRREEEEAAAADDDDSSSSTTTTDDDDIIIIOOOOOOOOFFFFFFFF, CCCCOOOONNNNFFFF____SSSSTTTTHHHHRRRREEEEAAAADDDDSSSSTTTTDDDDIIIIOOOOOOOONNNN, CCCCOOOONNNNFFFF____HHHHIIIISSSSTTTTRRRREEEESSSSEEEETTTT, CCCCOOOONNNNFFFF____HHHHIIIISSSSTTTTSSSSIIIIZZZZEEEE, CCCCOOOONNNNFFFF____HHHHIIIISSSSTTTTOOOONNNN, CCCCOOOONNNNFFFF____HHHHIIIISSSSTTTTOOOOFFFFFFFF, CCCCOOOONNNNFFFF____GGGGEEEETTTTSSSSIIIIZZZZEEEE, and CCCCOOOONNNNFFFF____GGGGEEEETTTTUUUUSSSSEEEERRRRSSSS never return an error. Otherwise, a value of -1 is returned and _eeee_rrrr_rrrr_nnnn_oooo is set to indicate the error. PPPPaaaaggggeeee 7777 
